Create deploy-to-pantheon.yml #5556
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kimsauce
approved these changes
Jul 8, 2025
Collaborator
kimsauce
left a comment
kimsauce
left a comment
There was a problem hiding this comment.
Thanks, @vfalconisumo ! To confirm, this is meant to trigger a push to production deployment only after a merge to main?
Collaborator
Author
|
@kimsauce correct, it will only run when a PR is merged or something is pushed to |
Collaborator
Author
|
@kimsauce I've added the secrets and variable to the repo |
Collaborator
thank you!! is this ok to merge? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose of this pull request
This pull request adds an additional, parallel GitHub workflow that builds and deploys the docs site to Sumo's marketing site. The purpose of this workflow is to QA deploying the site to Marketing's environment without disrupting the current process.
The workflow will fail without the following repo vars:
PANTHEON_SSH_KEYPANTHEON_KNOWN_HOSTSPANTHEON_MACHINE_TOKENPANTHEON_AUTH_USERPANTHEON_AUTH_PASSWORDPANTHEON_SITE_IDI have these ready to add to the repo in GitHub, but I won't add them until an owner gives me the OK. :)
Select the type of change
Ticket (if applicable)
Asana task